-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convert to aws sdk v3, switch to npm #51
Conversation
🤦🏽 I completely missed #48 but it looks like we did basically the same thing, with a few small differences. @zemberdotnet apologies for the duplication. If you're good with this, want to go with this one since it also includes node upgrade and doesn't require conflict resolution? I pulled in a couple key things from yours that I missed. |
|
Findings | ||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Dependency: npm / braces@ 3.0.2 Vulnerability Information
|
||||||||||||||||
Dependency Location https://github.com/JupiterOne/dynamodb-dao/blob/aa4732bc28e19a33bd139e95ef8e3c5864e2685c/package-lock.json |
Not a finding? Ignore it by adding a comment on the line with just the word noboost
.
Scanner: boostsecurity - BoostSecurity osv-scanner
breaking change. I think I'd like to switch to npm also before doing a major version bump